Cryptext x64 0.11x targeted tests
=================================

Build with the user's reference FASM 1.73.35. No build success is claimed by the
generation environment.

A. Folder shell encryption
1. Install/update with install_shell_user.cmd.
2. Right-click a normal filesystem folder; verify Cryptext Encrypt is present.
3. Folder tree suggestion:
     root\a.txt
     root\empty\
     root\sub\b.bin
     root\sub\deep\c.dat
     root\already.$#!   (known valid encrypted file)
4. Choose Encrypt, enter password, press OK.
5. Verify a.txt/b.bin/c.dat are each independently encrypted in their original
   directories and already.$#! is not double-encrypted.
6. Verify empty directories remain present.
7. Decrypt the resulting files individually and compare them byte-for-byte.
8. Optional: place a junction/symlink inside the tree and verify Cryptext does not
   traverse outside the selected tree.

B. Folder failure safety
1. Test an unreadable subdirectory if practical. Expansion should stop before any
   listed file is encrypted.
2. Very large trees that exceed the protected list buffer should report the list-size
   error before modifying files.

C. Existing file paths
- Single file shell Encrypt/Decrypt
- mixed multi-select
- file Drag & Drop
- command-line file paths
All must behave exactly as 0.11w fix1.

D. About icon
Open About and click repeatedly:
  key -> AES v2 -> AES v3 -> BeOS v4 -> key
Verify Explorer .$#! icon refreshes and the selected variant survives an update.

E. Vault PIN caret
Open vault setup/unlock, focus the PIN field and type digits physically. After every
digit, the caret should remain after the final bullet. Repeat with Backspace and with
the randomized numeric keypad.

F. Crypto regression
Re-test at least one CT64FILE v1 file and one known Cryptext 3.4 legacy file. Neither
crypto path was intentionally changed.
